Skip to content

dataset excluded from NNPDF4.0: CMS_1JET_7TEV_R07#2420

Open
andrpie wants to merge 6 commits intomasterfrom
implement_CMS_1JET_7TEV_R07
Open

dataset excluded from NNPDF4.0: CMS_1JET_7TEV_R07#2420
andrpie wants to merge 6 commits intomasterfrom
implement_CMS_1JET_7TEV_R07

Conversation

@andrpie
Copy link
Contributor

@andrpie andrpie commented Jan 20, 2026

This is the initial implementation.

  • the observable chosen is inclusive jet cross section with jet radius parameter R=0.7. There is another observable available, the same thing but with R=0.5. Should I implement both?
  • for each bin, there is a nonperturbative correction factor that ensures a data-theory agreement. Should these also be implemented?

experiment: CMS

implemented_observables:
- observable_name: R07
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe it is better to keep track of the type of the observable. You could use for example

Suggested change
- observable_name: R07
- observable_name: R07_PTY

@achiefa achiefa force-pushed the implement_CMS_1JET_7TEV_R07 branch from 76a0228 to 820cedc Compare January 30, 2026 17:40
pT: {description: jet transverse momentum, label: r"$p_T$" , units: GeV}
y: {description: jet rapidity, label: r"$|y|$" , units: ''}
sqrts: {description: centre of mass energy, label: r"$\sqrt(s)$", units: GeV}
kinematic_coverage: [pT, y, sqrts]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could please change this order?

Suggested change
kinematic_coverage: [pT, y, sqrts]
kinematic_coverage: [y, pT, sqrts]

Comment on lines +1 to +13
bins:
- y:
min: 0.0
mid: 0.25
max: 0.5
sqrts:
min: null
mid: 7000.0
max: null
pT:
min: 56.0
mid: 60.0
max: 64.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note that the ordering here is different from the one in metadata.yaml (see kinematic_coverage).

@enocera
Copy link
Contributor

enocera commented Feb 24, 2026

This is the initial implementation.

* the observable chosen is inclusive jet cross section with jet radius parameter R=0.7. There is another observable available, the same thing but with R=0.5. Should I implement both?

* for each bin, there is a nonperturbative correction factor that ensures a data-theory agreement. Should these also be implemented?

Dear @andrpie let me try to clarify some delicate points that we need to keep in mind with this data set.

  1. We want to implement the most recent measurement arXiv:1406.0324, consistently with what we did in NNPDF4.0. The measurement is available for values of the jet radius of 0.5 and 0.7.
  2. The NNLO ploughshare grids are unfortunately not available for this measurement. They are, however, for the previous measurement arXiv:1212.6660, albeit only for R=0.7 and for a slightly different binning.
    The two measurements are based on an analysis of the same rawdata (same data taking period, same luminosity). The kinematic binning of the two measurements overlaps, albeit not exactly: 1406.0324 has more bins at low pT (that we would cut anyways), whereas 1212.6660 has a couple more bins at large pT.

Because of 1) and 2), the idea is to implement only the most recent measurement with R=0.7 for NNPDF4.1. There are therefore three tasks.

  • Implement the data set in commondata
  • Take the relevant grids from plougshare and convert them to PineAPPL grids
  • Make sure to take the bins that are the intersection of those in 1212.6660 and in 1406.0324 and match them to the points available from the grids.

As soon as you're done with the first two points, I can help with the third.

@achiefa
Copy link
Contributor

achiefa commented Feb 24, 2026

Hi @enocera, thanks for your comment. I can also help if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants